SCRUM Quality, Planning, and Completion: Effective User Stories
SCRUM Quality, Planning, and Completion: Effective User Stories
- discover the key concepts covered in this course
- define the purpose of user stories in Scrum
- describe the increasing level of detail in user stories
- recognize when the level of detail is appropriate for a user story
- recognize that user stories may be written from different perspectives
- define compound and complex user stories
- describe techniques for splitting user stories
- distinguish between user stories and tasks
- describe techniques for estimating user stories
- recognize common user story mistakes
- summarize the key concepts covered in this course
The user story is a central part of Scrum, as it represents product requirements from the perspective of the user and provides a common language for the scrum team to communicate with stakeholders.
This course presents the concepts associated with creating user stories and using them to identify product requirements. You'll learn about the user story structure, the criteria that a user story should meet, how to split a story, and how user stories can be used to establish a shared product vision.
SCRUM Quality, Planning, and Completion: Quality & Productivity
SCRUM Quality, Planning, and Completion: Quality & Productivity
- discover the key concepts covered in this course
- recognize the purpose of quality management in Scrum
- recognize the roles and authority related to quality decisions
- recognize the relationship between product testing and Scrum
- recognize quality metrics that validate fulfillment of the sprint goal
- recognize productivity metrics that validate fulfillment of the sprint goal
- recognize the balance between quality and productivity
- describe Scrum factors that affect quality
- define the role of the scrum master in managing productivity and quality
- summarize the key concepts covered in this course
Sprint planning makes use of various consensus and estimation techniques in an effort to define a measurable sprint goal for the product owner, team, and stakeholders. The sprint goal should define what is going to be completed during the course of the current sprint.
This course presents the concepts associated with setting sprint goals and planning for the sprint. You'll learn about the Definition of Done, how to define the increment, how to estimate the sprint backlog, and how to avoid common mistakes. Commonly used tools and techniques, and ways to conduct effective sprint meetings are also covered.
SCRUM Quality, Planning, and Completion: The Definition of Done
SCRUM Quality, Planning, and Completion: The Definition of Done
- discover the key concepts covered in this course
- recognize the five levels of planning within the Scrum framework
- describe how the product scope evolves throughout the project life cycle
- describe how the Definition of Done is used in product development
- recognize the impact of Definition of Done on product quality
- recognize variations of the Definition of Done concept
- identify the steps in creating a Definition of Done
- describe the relationship between the Definition of Done and the sprint goal
- recognize how a clear Definition of Done supports the three pillars of Scrum empiricism
- summarize the key concepts covered in this course
As a product evolves from a high level vision to more detailed requirements, the team will establish a Definition of Done. This ensures transparency and a shared product vision, as well as that the team understands the work and can set realistic goals as features are about to be developed.
In this course, you'll learn the concepts associated with defining done, determining the appropriate amount of detail for the level of planning, and the relationship between definition of done and quality, empiricism, and the sprint goal.
